Information processing apparatus, diagnosis control apparatus, and communication apparatus

ABSTRACT

An information processing apparatus includes a communication apparatus and a different communication apparatus connected to the communication apparatus via a plurality of transmission paths. The communication apparatus includes a transmitting unit and a control unit. In response to designation of a transmission path targeted for diagnosis, selected amongst the transmission paths while the communication apparatus is in a state capable of data communication with the different communication apparatus using the transmission paths, the transmitting unit transmits a test signal to the targeted transmission path while the state capable of data communication with the different communication apparatus is maintained using remaining transmission paths of the transmission paths other than the targeted transmission path. The control unit diagnoses the presence or absence of an abnormality sign in the targeted transmission path based on the result of detecting the test signal in the targeted transmission path and outputs the diagnostic result.

CROSS-REFERENCE TO RELATED APPLICATION

This application is based upon and claims the benefit of priority of the prior Japanese Patent Application No. 2016-191805, filed on Sep. 29, 2016, the entire contents of which are incorporated herein by reference.

FIELD

The embodiments discussed herein are related to an information processing apparatus, a diagnosis control apparatus, and a communication apparatus.

BACKGROUND

Serial transmission has increasingly been employed to achieve high-speed signal transmission within information processing apparatuses as well as between information processing apparatuses and their peripherals. PCI Express (Peripheral Component Interconnect Express), hereinafter abbreviated as PCIe, and SAS (Serial-Attached SCSI (Small Computer System Interface)) are major standards for such high-speed serial transmission. These standards use a plurality of serial transmission paths bundled together, providing high-speed data transmission.

As technology using PCIe, the following information transmission apparatus, for example, has been proposed. Upon detecting an energy-saving switchover event, the information transmission apparatus enters a power saving mode by putting one lane amongst a plurality of lanes into an effective state while placing the remaining lanes into an idle state.

Japanese Laid-open Patent Publication No. 2010-147702

Sudden communication failure sometimes occurs when communication between communication circuits by high-speed serial transmission described above is in progress. Such communication failure may be attributed to aging degradation of a capacitor, such as an alternating current (AC) coupling capacitor, on a transmission path. Performing diagnosis to detect an abnormality sign of forthcoming communication failure may be considered as one way of dealing with this problem; however, in order to perform the diagnosis, the communication needs to be interrupted.

SUMMARY

According to an aspect, there is provided an information processing apparatus including a first communication apparatus; and a second communication apparatus configured to be connected to the first communication apparatus via a plurality of transmission paths. The first communication apparatus includes a transmitter configured to transmit, in response to designation of a transmission path targeted for diagnosis, selected amongst the transmission paths while the first communication apparatus is in a state capable of data communication with the second communication apparatus using the transmission paths, a test signal to the targeted transmission path while the state capable of data communication with the second communication apparatus is maintained by use of remaining transmission paths of the transmission paths other than the targeted transmission path; and a processor configured to perform a procedure including diagnosing presence or absence of an abnormality sign in the targeted transmission path based on a result of detecting the test signal in the targeted transmission path and outputting a diagnostic result.

The object and advantages of the invention will be realized and attained by means of the elements and combinations particularly pointed out in the claims.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are not restrictive of the invention.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 illustrates a configuration and operation example of an information processor according to a first embodiment;

FIG. 2 illustrates an example of a storage system according to a second embodiment;

FIG. 3 illustrates an example of hardware configurations of controller modules;

FIG. 4 illustrates an example of a hardware configuration of a device enclosure;

FIG. 5 illustrates an example of inter-circuit lane counts inside a storage device;

FIG. 6 illustrates an example of configurations and connection topology of interface circuits;

FIG. 7 illustrates an example of a configuration of a lane;

FIG. 8 is a first diagram illustrating changes in voltage in response to transmission of a test signal;

FIG. 9 is a second diagram illustrating the changes in voltage in response to transmission of the test signal;

FIG. 10 illustrates a first example of switch connection status;

FIG. 11 is a second example of the switch connection status;

FIG. 12 is a third example of the switch connection status;

FIG. 13 is a block diagram illustrating a configuration example of processing functions of a controller module;

FIG. 14 illustrates an example of a diagnosis target channel table;

FIG. 15 illustrates an example of result management tables;

FIG. 16 is a flowchart illustrating an example of a diagnostic process at link-up;

FIG. 17 is a first flowchart illustrating an example of a determining process;

FIG. 18 is a second flowchart illustrating the example of the determining process;

FIG. 19 is a flowchart illustrating an example of a diagnostic result receiving process;

FIG. 20 is a first sequence diagram illustrating an example of a diagnosis control process during normal operation;

FIG. 21 is a second sequence diagram illustrating the example of the diagnosis control process during normal operation;

FIG. 22 is a flowchart illustrating an example of a diagnostic process performed by each interface circuit during normal operation;

FIG. 23 is a first flowchart illustrating an example of an abnormality handling process;

FIG. 24 is a second flowchart illustrating the example of the abnormality handling process;

FIG. 25 is a sequence diagram illustrating an example of a diagnostic process performed when a port has a small number of lanes;

FIG. 26 illustrates an example of lane counts in a storage device according to a third embodiment; and

FIG. 27 illustrates an example of an internal configuration of an interface circuit according to the third embodiment.

DESCRIPTION OF EMBODIMENTS

Several embodiments will be described below with reference to the accompanying drawings, wherein like reference numerals refer to like elements throughout.

(a) First Embodiment

FIG. 1 illustrates a configuration and operation example of an information processor according to a first embodiment. An information processor 10 illustrated in FIG. 1 includes communication devices 11 and 12. The communication devices 11 and 12 are connected to each other via transmission paths 1 to 3. The communication devices 11 and 12 are communication interfaces that communicate with each other via the transmission paths 1 to 3, each of which is a serial transmission path. The communication device 11 is able to bundle, amongst the transmission paths 1 to 3, a plurality of transmission paths together to transmit data to the communication device 12. Note that the number of transmission paths between the communication devices 11 and 12 is here three (the transmission paths 1 to 3) for the purpose of illustration; however, the communication devices 11 and 12 may be connected to each other via any number of transmission paths greater than or equal to two.

The communication device 11 includes a transmitting unit 11 a and a control unit 11 b. In the communication device 11, the following operations take place when a transmission path targeted for diagnosis of the presence or absence of an abnormality sign is designated from among the transmission paths 1 to 3 while the communication device 11 remains in a state capable of data communication with the communication device 12 using the transmission paths 1 to 3. Assume here that the transmission path 1, for example, is designated as the targeted transmission path. The state capable of data communication may include, for example, a state capable of data transmission and reception, a state with data being transmitted, and a state with data being received.

The transmitting unit 11 a transmits a diagnostic test signal through the transmission path 1 designated as the targeted transmission path amongst the transmission paths 1 to 3 while the state capable of data communication with the communication device 12 is maintained by use of the remaining transmission paths 2 and 3. The transmitting unit 11 a may have a function of receiving data from the communication device 12. The control unit 11 b diagnoses the presence or absence of an abnormality sign in the transmission path 1 based on the result of detecting the test signal in the transmission path 1, and outputs the diagnostic result. Herewith, the communication device 11 is able to make a diagnosis of an abnormality sign in the transmission path 1 while keeping communication with the communication device 12. That is, it is possible to determine whether a communication abnormality is likely to develop in the transmission path 1 based on the result of detecting the test signal in the transmission path 1 while data communication is normally carried out.

The transmitting unit 11 a may include, for example, a test signal outputting unit 11 a 1, a data outputting unit 11 a 2, and a switch 11 a 3, as illustrated in FIG. 1. The test signal outputting unit 11 a 1 outputs a test signal to one of input terminals on the switch 11 a 3. The data outputting unit 11 a 2 supplies data to be transmitted to the communication device 12 by distributing the data across input terminals on the switch 11 a 3, whose number is the same as the number of the transmission paths 1 to 3. The switch 11 a 3 switches connection lines between these input terminals and the transmission paths 1 to 3 according to an instruction from the control unit 11 b.

In the case of implementing data transmission to the communication device 12 using the transmission paths 1 to 3, the control unit 11 b controls the switch 11 a 3 in such a manner that, amongst all the input terminals provided on the switch 11 a 3, individual input terminals connected to the data outputting unit 11 a 2 are connected one-to-one to the transmission paths 1 to 3. On the other hand, in the case of performing diagnosis on the transmission path 1, for example, the control unit 11 b controls the switch 11 a 3 in such a manner as to change the connection of the transmission path 1 on the switch 11 a 3 to, amongst all the input terminals of the switch 11 a 3, an input terminal connected to the test signal outputting unit 11 a 1. This enables diagnosis on the transmission path 1 while allowing the data outputting unit 11 a 2 to continue data transmission using the transmission paths 2 and 3.

Note that the targeted transmission path may be designated, for example, by a diagnosis control device 13. For example, the diagnosis control device 13 sequentially designates a targeted transmission path amongst the transmission paths 1 to 3 and notifies the communication device 11 of the designation. Herewith, the communication device 11 is able to perform diagnosis of a communication abnormality on each of the transmission paths 1 to 3 while continuing communication with the communication device 12. The diagnostic results may be transmitted to the diagnosis control device 13 from the control unit 11 b. Such a diagnosis control device 13 may be provided inside the information processor 10, as illustrated in the example of FIG. 1.

The diagnosis of an abnormality sign in each of the transmission paths 1 to 3 is performed in the following manner, for example. Note that, as a test signal, a pulse signal is used, for example. When the communication device 11 starts communication with the communication device 12, the control unit 11 b causes the transmitting unit 11 a to transmit test signals through the individual transmission paths 1 to 3. With respect to each of the transmission paths 1 to 3, the control unit 11 b detects the rise time of rising transitions of the test signal in a waveform, and stores the detected rise time in memory of the communication device 11, for example.

Subsequently, communication between the communication devices 11 and 12 is started, and a targeted transmission path is designated when data communication to the communication device 12 is in progress using the transmission paths 1 to 3. Assuming that the transmission path 1 is designated as the targeted transmission path, the transmitting unit 11 a transmits a diagnostic test signal through the transmission path 1 while maintaining the data transmission to the communication device 12 by use of the remaining transmission paths 2 and 3, as described above. The control unit 11 b determines whether the rise time of the test signal in a waveform, detected for the transmission path 1 lies within a determination range. The determination range is determined on the basis of the rise time detected for the transmission path 1 at the start of the communication. If the detected rise time lies outside the determination range, the control unit 11 b determines that an abnormality sign is present in the transmission path 1.

The above-described diagnostic approach allows the control unit 11 b to determine whether a capacitor, such as an AC coupling capacitor, inserted into the transmission path 1 has increasingly degraded with age. The communication device 11 is able to perform such diagnosis while continuing data communication by use of the remaining transmission paths 2 and 3, as described above.

(b) Second Embodiment

Next described is a storage system in which a storage device is employed as an example of the information processor 10 of FIG. 1. FIG. 2 illustrates an example of a storage system according to a second embodiment. The storage system includes a storage device 100 and a host device 400. The storage device 100 and the host device 400 are connected to each other via a storage area network (SAN) using a protocol such as the Fibre Channel (FC) or Internet Small Computer System Interface (iSCSI).

The storage device 100 includes controller modules (CMs) 200 a and 200 b and a device enclosure (DE) 300. The controller modules 200 a and 200 b are storage control devices for controlling access to memory devices installed in the device enclosure 300 at the request of the host device 400. One of the controller modules 200 a and 200 b, for example, operates as an active-system controller module while the other one operates as a standby-system controller module. Alternatively, the controller modules 200 a and 200 b may individually implement access control to separate logical memory areas.

The device enclosure 300 is a disk array device with hard disk drives (HDDs) serving as memory devices to be accessed from the host device 400. Note that the device enclosure 300 may be equipped, for example, with a different type of memory devices, such as solid state drives (SSDs) in place of the HDDs. The host device 400 accesses the HDDs installed in the device enclosure 300 via the controller module 200 a or 200 b.

FIG. 3 illustrates an example of hardware configurations of controller modules. The controller module 200 a includes a central processing unit (CPU) 201 a, random access memory (RAM) 202 a, a PCIe switch 203 a, a channel adapter (CA) 204 a, an In/Out controller (IOC) 205 a, a SAS expander 206 a, a platform controller hub (PCH) 207 a, a SSD 208 a, a field programmable gate array (FPGA) 209 a, and flash memory 209 a 1. The controller module 200 b includes a CPU 201 b, RAM 202 b, a PCIe switch 203 b, a channel adapter (CA) 204 b, an IOC 205 b, a SAS expander 206 b, a PCH 207 b, a SSD 208 b, a FPGA 209 b, and flash memory 209 b 1. The controller modules 200 a and 200 b have the same hardware configuration. Therefore, the following description in the second embodiment focuses mainly on the hardware configuration of the controller module 200 a while appropriately omitting repeated explanation of the hardware configuration of the controller module 200 b.

Overall control of the controller module 200 a is exercised by the CPU 201 a. The CPU 201 a may be a multi-processor including a plurality of processing components. The RAM 202 a is used as a main memory device of the controller module 200 a, and temporarily stores therein at least part of programs to be executed by the CPU 201 a and various types of data to be used in the processing of the programs. The PCIe switch 203 a is connected to the CPU 201 a via a PCIe bus. The PCIe switch 203 a is also connected to the PCIe switch 203 b in the other controller module 200 b via a PCIe cable. The CPUs 201 a and 201 b communicate with each other through the communication channel open between the PCIe switches 203 a and 203 b. For example, through this communication channel, each of the CPUs 201 a and 201 b is able to transmit data stored in its RAM 202 a/202 b to the CPU 201 a/201 b in the other controller module 200 a/200 b.

The channel adapter 204 a is connected to the CPU 201 a via a PCIe bus. The channel adapter 204 a performs interface processing, such as data transmission and reception, between the CPU 201 a and the host device 400. The IOC 205 a is connected to the CPU 201 a via a PCIe bus. The IOC 205 a is also connected to the SAS expanders 206 a and 206 b via SAS cables. The IOC 205 a performs interface processing between the CPU 201 a and the HDDs installed in the device enclosure 300. The SAS expander 206 a is connected to the IOC 205 a and also connected to the IOC 205 b via SAS cables. In addition, the SAS expander 206 a is connected to the device enclosure 300 via a SAS cable. The SAS expander 206 a relays data between the IOCs 205 a and 205 b and the HDDs in the device enclosure 300.

Note here that the IOC 205 a is connected to the device enclosure 300 via the SAS expander 206 a. At the same time, the IOC 205 a is also connected to the device enclosure 300 via the SAS expander 206 b. Thus, the IOC 205 a and the device enclosure 300 are connected with each other via the two SAS expanders 206 a and 206 b, thereby providing redundant access channels from the IOC 205 a to the device enclosure 300. In like fashion, the IOC 205 b is connected to the device enclosure 300 via the SAS expander 206 b. At the same time, the IOC 205 b is also connected to the device enclosure 300 via the SAS expander 206 a. Thus, the IOC 205 b and the device enclosure 300 are connected with each other via the two SAS expanders 206 a and 206 b, thereby also providing redundant access channels from the IOC 205 b to the device enclosure 300.

The PCH 207 a performs data transmission and reception between the CPU 201 a and the SSD 208 a or the FPGA 209 a. The SSD 208 a is used as a secondary memory device of the controller module 200 a, and stores, for example, firmware to be executed by the CPU 201 a. Note that a different type of non-volatile memory device, such as a HDD, may be used as the secondary memory device.

The FPGA 209 a monitors the presence or absence of an abnormality in each component of the controller module 200 a. As such an abnormality monitoring function, the FPGA 209 a according to this embodiment has a function of controlling diagnosis for detecting abnormalities in PCIe and SAS channels inside the storage device 100. Note that the FPGA 209 a includes, for example, a processor capable of executing programs and memory capable of temporarily storing data associated with the programs. In this case, the abnormality monitoring function of the FPGA 209 a is implemented, for example, by execution of a program stored in the flash memory 209 a 1 by the processor of the FPGA 209 a. The flash memory 209 a 1 stores information to be used in processing performed by the FPGA 209 a. The FPGAs 209 a and 209 b are connected with each other in such a manner as to allow mirroring of data stored, for example, in the flash memory 209 a 1 to the other flash memory 209 b 1.

FIG. 4 illustrates an example of a hardware configuration of a device enclosure. The device enclosure 300 includes SAS expanders 311 a and 311 b and HDDs 312 a, 312 b, 312 c and so on. The SAS expander 311 a is connected to the SAS expander 206 a and also connected to the HDDs 312 a, 312 b, 312 c and so on via SAS cables. The SAS expander 311 a relays data between the SAS expander 206 a and the HDDs 312 a, 312 b, 312 c and so on. The SAS expander 311 b is connected to the SAS expander 206 b and also connected to the HDDs 312 a, 312 b, 312 c and so on via SAS cables. The SAS expander 311 b relays data between the SAS expander 206 b and the HDDs 312 a, 312 b, 312 c and so on.

As for PCIe and SAS communication, a plurality of serial transmission paths are aggregated into a single port to facilitate high-speed data transmission. Each serial transmission path here includes a total of four signal lines, a pair of differential signal lines for transmission and a pair of differential signal lines for reception. Such a serial transmission path in PCIe is referred to as a “lane”. For ease of explanation, the term “lane” is used to refer to not only a PCIe serial transmission path but also a SAS serial transmission path in the following description.

FIG. 5 illustrates an example of inter-circuit lane counts inside a storage device. Four lanes are used to connect the CPU 201 a and the PCIe switch 203 a. Four lanes are used to connect the CPU 201 a and the channel adapter 204 a. Eight lanes are used to connect the CPU 201 a and the IOC 205 a. Four lanes are used to connect the CPU 201 a and the PCH 207 a. Four lanes are used to connect the IOC 205 a and the SAS expander 206 a. One lane is used to connect the SAS expander 206 a and the SAS expander 311 a (see FIG. 4) of the device enclosure 300.

Four lanes are used to connect the CPU 201 b and the PCIe switch 203 b. Four lanes are used to connect the CPU 201 b and the channel adapter 204 b. Eight lanes are used to connect the CPU 201 b and the IOC 205 b. Four lanes are used to connect the CPU 201 b and the PCH 207 b. Four lanes are used to connect the IOC 205 b and the SAS expander 206 b. One lane is used to connect the SAS expander 206 b and the SAS expander 311 b (see FIG. 4) of the device enclosure 300. Four lanes are used to connect the PCIe switches 203 a and 203 b. Four lanes are used to connect the IOC 205 a and the SAS expander 206 b. Four lanes are used to connect the IOC 205 b and the SAS expander 206 a.

As illustrated in FIG. 5, each port is equipped with an interface circuit to perform communication through the lanes connected to the port. Each PCIe port is equipped with a PCIe interface to perform communication according to the PCIe standard, and each SAS port is equipped with a SAS interface to perform communication according to the SAS standard. In the example of FIG. 5, PCIe interfaces are provided for the CPUs 201 a and 201 b, the PCIe switches 203 a and 203 b, the channel adapters 204 a and 204 b, the IOCs 205 a and 205 b, and the PCHs 207 a and 207 b. SAS interfaces are provided for the IOCs 205 a and 205 b, the SAS expanders 206 a and 206 b, and the SAS expanders 311 a and 311 b. Both PCIe and SAS interfaces are provided for the IOC 205 a and 205 b. The PCIe and SAS interfaces have the same basic configuration. Therefore, the following description makes no distinction between these two types of interface circuits.

FIG. 6 illustrates an example of configurations and connection topology of interface circuits. The example of FIG. 6 depicts interface circuits 21 a and 21 b connected to each other by four lanes 22 a to 22 d. That is, in the example of FIG. 6, each of the interface circuits 21 a and 21 b performs mutual communication using up to four lanes as a single logical communication port. The interface circuit 21 a includes transmitting/receiving units 210 a to 210 d, a control circuit 220 a, memory 230 a, a pulse generator (PG) 240 a, a multiplexer/demultiplexer (MUX/DEMUX) 250 a, and a switch 260 a. The interface circuit 21 b includes transmitting/receiving units 210 e to 210 h, a control circuit 220 b, memory 230 b, a pulse generator 240 b, a MUX/DEMUX 250 b, and a switch 260 b.

The transmitting/receiving unit 210 a is connected to the transmitting/receiving unit 210 e via the lane 22 a. The transmitting/receiving unit 210 b is connected to the transmitting/receiving unit 210 f via the lane 22 b. The transmitting/receiving unit 210 c is connected to the transmitting/receiving unit 210 g via the lane 22 c. The transmitting/receiving unit 210 d is connected to the transmitting/receiving unit 210 h via the lane 22 d. Each of the transmitting/receiving units 210 a to 210 h controls data transmission and reception with the transmitting/receiving unit at the other endpoint. Each of the lanes 22 a, 22 b, 22 c, and 22 d is differential signal line pairs composed of a pair (2) of signal lines for transmission from one side and a pair (2) of signal lines for transmission from the other side, as described above. Note that the transmitting/receiving units 210 a to 210 d are connected to the differential signal line pairs that make up the lanes 22 a to 22 d, respectively, via a common connector. In like fashion, the transmitting/receiving units 210 e to 210 h are connected to the differential signal line pairs that make up the lanes 22 a to 22 d, respectively, via a common connector.

The control circuit 220 a controls the pulse generator 240 a, the MUX/DEMUX 250 a, and the switch 260 a. The control circuit 220 a is configured to communicate with the CPU 201 a, and carries out, for example, switching of the number of lanes to be used and lane diagnosis control (to be described later) according to an instruction from the CPU 201 a. The memory 230 a stores therein various types of data to be used by the control circuit 220 a for its processing. Note that the control circuit 220 a may include a processor, and at least part of the processing of the control circuit 220 a may be implemented by the processor executing a firmware program stored in the memory 230 a.

The pulse generator 240 a is a circuit for outputting a diagnostic test signal (pulse signal) for detecting an abnormality or abnormality sign in a lane. The MUX/DEMUX 250 a distributes data to be transmitted to the interface circuit 21 b across the transmitting/receiving units 210 a to 210 d. In addition, the MUX/DEMUX 250 a receives, from the transmitting/receiving units 210 a to 210 d, data received from the interface circuit 21 b. The switch 260 a switches connection lines between output terminals of the MUX/DEMUX 250 a individually corresponding to the lanes 22 a to 22 d as well as an output terminal of the pulse generator 240 a and input terminals of the individual transmitting/receiving units 210 a to 210 d. Details of the switch 260 a are described later. Note that signals received by the transmitting/receiving units 210 a to 210 d are directly input to the MUX/DEMUX 250 a without the switch 260 a.

Functions of the control circuit 220 b, the memory 230 b, the pulse generator 240 b, the MUX/DEMUX 250 b, and the switch 260 b are the same as those of the control circuit 220 a, the memory 230 a, the pulse generator 240 a, the MUX/DEMUX 250 a, and the switch 260 a, respectively, and repeated descriptions thereof are omitted.

FIG. 7 illustrates an example of a configuration of a lane. The example of FIG. 7 depicts the lane 22 a connecting the transmitting/receiving units 210 a and 210 e. The transmitting/receiving unit 210 a includes a transmission (Tx) driver 211 a, a reception (Rx) driver 212 a, and a detection circuit 213 a. The Tx driver 211 a converts transmission data input from the MUX/DEMUX 250 a via the switch 260 a or a test signal input from the pulse generator 240 a via the switch 260 a into a differential signal and then outputs the differential signal. The Rx driver 212 a converts a differential signal received from the transmitting/receiving unit 210 e into a signal of a predetermined format and then outputs the converted signal to the MUX/DEMUX 250 a.

In the case where a test signal is input to the Tx driver 211 a, the detection circuit 213 a monitors the voltage of a differential signal output from the Tx driver 211 a. Then, the detection circuit 213 a detects the time for the voltage to rise from a predetermined lower threshold to a predetermined upper threshold, and notifies the control circuit 220 a of the detected time. The lower threshold is used to detect the start of a rise in the test signal, and the upper threshold is used to detect the end of a rise in the test signal. Therefore, by using the lower and upper thresholds, the detection circuit 213 a is able to detect the rise time of the test signal.

Note that, in practice, the transmitting/receiving unit 210 a further includes, for example, a serializer, a Tx equalizer, a Rx equalizer, and a deserializer. The serializer serializes transmission data or a test signal input thereto and then outputs the serialized data or signal to the Tx driver 211 a. The Tx equalizer performs a waveform equalization to a signal output from the Tx driver 211 a. As a transmitter equalization technique, pre-emphasis or preshoot, for example, is employed here. The detection circuit 213 a may detect the rise time of a test signal output from the Tx equalizer. The Rx equalizer performs waveform equalization to a differential signal received from the transmitting/receiving unit 210 e and then outputs the equalized signal to the Rx driver 212 a. As a receiver equalization technique, Decision Feedback Equalization (DFE) or Feed-Forward Equalization (FFE), for example, is employed here. The deserializer converts a serial signal output from the Rx driver 212 a into a parallel signal and then outputs the parallel signal to the MUX/DEMUX 250 a.

On the other hand, the transmitting/receiving unit 210 e includes a Tx driver 211 b, a Rx driver 212 b, and a detection circuit 213 b. Functions of the Tx driver 211 b, the Rx driver 212 b, and the detection circuit 213 b are the same as those of the Tx driver 211 a, the Rx driver 212 a, and the detection circuit 213 a, respectively, and repeated descriptions thereof are omitted.

As for the differential signal lines extending from the transmitting/receiving unit 210 a to the transmitting/receiving unit 210 e, AC coupling capacitors C1 a and C2 a are connected in series at the transmitting ends of the individual differential signal lines, and one sides of individual termination resistors R1 a and R2 a whose other sides are grounded are connected at the receiving ends. The AC coupling capacitors C1 a and C2 a are provided internally or externally to the transmitting-side transmitting/receiving unit 210 a to delete a direct-current (DC) component. Each of the termination resistors R1 a and R2 a has a resistance value (for example, 50Ω) defined by a communication standard concerned. The termination resistors R1 a and R2 a are provided internally to the receiving-side transmitting/receiving unit 210 e to prevent a transmission signal from being reflected at the receiving end. As for the differential signal lines extending from the transmitting/receiving unit 210 e to the transmitting/receiving unit 210 a, AC coupling capacitors C1 b and C2 b are connected in series at the transmitting ends of the individual differential signal lines, and one sides of individual termination resistors R1 b and R2 b whose other sides are grounded are connected at the receiving ends.

Next described is diagnosis of lanes performed by an interface circuit. The interface circuit performs diagnosis of lanes by transmitting a pulsed test signal from the pulse generator to each lane and detects a rise timing of the voltage at the transmitting ends of the differential signal lines. This diagnosis includes two components: diagnosis to detect an abnormality in each lane; and diagnosis to detect an abnormality sign in each lane. The former diagnosis is performed at link-up right after the other endpoint interface circuit is newly connected. The latter diagnosis is basically performed during normal operation when communication with the other endpoint interface circuit is in progress after link-up.

The following describes a diagnostic approach implemented by the transmitting/receiving unit 210 a of the interface circuit 21 a as an example. FIG. 8 is a first diagram illustrating changes in the voltage in response to transmission of a test signal. The voltage of FIG. 8 is the voltage of a differential signal detected by the detection circuit 213 a when a test signal is transmitted from the Tx driver 211 a of the transmitting/receiving unit 210 a. In addition, the time origin (time=0) in FIG. 8 corresponds to when the voltage detected by the detection circuit 213 a exceeds a predetermined lower threshold (i.e., the rise start time). Further, voltage v1 is an upper threshold used to determine the rise completion time. Note that these are the same for FIG. 9.

In FIG. 8, time t1 represents an example of a rise time of the test signal obtained when an interface circuit is not connected to the interface circuit 21 a at the other endpoint. On the other hand, time t2 represents an example of a rise time of the test signal obtained when an interface circuit (in this example, the interface circuit 21 b of FIG. 6) is connected to the interface circuit 21 a at the other endpoint. When the other endpoint interface circuit 21 b is connected, the termination resistors R1 a and R2 a of the interface circuit 21 b are connected to the differential signal lines, which results in the test signal having a longer rise time.

Serial communication standards, such as PCIe and SAS, specify device detection procedures to determine, at link-up, whether an interface circuit is connected at the other endpoint based on such a difference in rise time of the test signal attributed to the presence or absence of termination resistors. Such a detection procedure defines a rise time threshold based on specifications of a circuit, such as a termination resistor. Then, in the case where the detected rise time of the test signal at link-up is equal to or more than the threshold, an interface circuit is determined to be connected at the other endpoint. The interface circuit 21 a of this embodiment also has such a device detection function.

In addition to the device detection function, the interface circuit 21 a also has a function of diagnosing the occurrence of an abnormality in a lane in the case where an interface circuit is determined to be connected at the other endpoint. In this diagnosis, the control circuit 220 a of the interface circuit 21 a determines whether the rise time of the test signal detected at link-up falls within a range from time L1 to time L2 (hereinafter referred to as the “first normal range”). If the detected rise time falls within the first normal range, the control circuit 220 a determines that the lane is normal. On the other hand, if the detected rise time falls outside the first normal range, the control circuit 220 determines that the lane has an abnormality. For example, in the case where time t3 illustrated in FIG. 8 is detected as the rise time, the control circuit 220 a determines that the lane has an abnormality because the time t3 falls outside the first normal range.

This diagnosis allows detection of an abnormal rise time attributed to an abnormality of some sort occurring in a device on the lane. In the case where an abnormal rise time is observed, normal signal transmission in the diagnosis target lane may fail. When an abnormality has been detected in this diagnosis, the occurrence of a communication abnormality would be prevented, for example, by performing communication without the use of the lane with an abnormality. Note that manufacturing variations in internal circuits (for example, serializer-deserializer (SERDES) circuits) of the transmitting/receiving unit 210 a and the other endpoint transmitting/receiving unit 210 e are found to be a cause of such an abnormal rise time.

As for the times L1 and L2 used as thresholds, predetermined values are employed separately for PCIe interfaces and SAS interfaces. The first normal range is set in such a manner as to include at least a normal rise time according to a standard concerned. In addition, the time L1 is a time point more than a threshold time used in the device detection procedure to determine that an interface circuit is connected at the other endpoint. Herewith, even when an interface circuit has been determined to be connected at the other endpoint, it is possible to determine whether the detected rise time is abnormal.

FIG. 9 is a second diagram illustrating the changes in the voltage in response to transmission of a test signal. The diagnosis to detect an abnormality sign in a lane is explained with reference to FIG. 9. Capacitors on a lane like the AC coupling capacitors C1 a, C2 a, C1 b, and C2 b of FIG. 7 normally have a resistance value of about hundreds of megaohms (MΩ). However, if an abnormality such as a crack develops in such a capacitor, the resistance value gradually decreases. As the capacitor increasingly degrades with age and the severity of the abnormality becomes worse, the resistance value may be reduced to about hundreds of ohms.

The rise time of the differential signal is shortened with a decrease in the resistance value, which causes a high incidence of sudden link down during normal operation. In view of this problem, the interface circuit 21 a transmits a test signal to each lane during normal operation and detects the rise time of the test signal. The control circuit 220 a of the interface circuit 21 a determines whether the detected rise time falls within a second normal range, which is narrower than the first normal range. If the detected rise time does not fall within the second normal range, the control circuit 220 a determines that an abnormality sign is present in the lane.

The second normal range is set in the following manner. The control circuit 220 a determines the second normal range with reference to the time t2 detected at link-up. Specifically, the control circuit 220 a subtracts a predetermined value from the time t2 to obtain a lower limit time L3 of the second normal range. Then, the control circuit 220 a adds the predetermined value to the time t2 to obtain an upper limit time L4 of the second normal range. Thus, setting the second normal range with reference to the time t2 detected at link-up facilitates estimating the progress of degradation of capacitors with age.

As described above, the second normal range is set to be narrower than the first normal range. This allows detection of a sign of an abnormality subsequently developing in a lane over time even if the lane is determined to have no abnormality at link-up and is capable of normal communication at the moment. Assume for example that a time t4 is detected as the rise time of the test signal in a diagnosis target lane during normal operation, as illustrated in FIG. 9. Because the time t4 falls within the first normal range, the diagnosis target lane is determined to have no abnormality at link-up, and is able to carry out normal communication at present. However, when the rise time is determined to fall outside the second normal range, the presence of an abnormality sign is detected, which raises an alert on the diagnosis target lane being at high risk for developing communication failure later.

Detection of such an abnormality sign allows the controller module 200 a (or 200 b) to implement a range of measures to reduce the effect of a communication abnormality in the lane possibly taking place later. For example, the controller module 200 a stops communication on the lane in which an abnormality sign has been detected, to thereby prevent the occurrence of port link-down due to a communication failure on the lane. Alternatively, the controller module 200 a issues an alert when an abnormality sign is detected to urge the user to replace components of the interface circuit or ones on the lane.

The above-described diagnosis to detect an abnormality sign is performed during normal operation. Conventional interface circuits are not capable of performing such diagnosis without stopping port communication during normal operation. On the other hand, serial communication standards, such as PCIe, define a power saving state (“L0s” state) in which communication on at least one of a plurality of serial transmission paths bundled together is shut down. In view of this, each interface circuit of this embodiment enables diagnosis on a diagnosis target lane while continuing communication on lanes other than the diagnosis target lane, by use of a state transition function of entering the L0s state and a switch for physically isolating the diagnosis target lane from the remaining lanes.

FIG. 10 illustrates a first example of switch connection status. First, a configuration example of the switch 260 a and its peripheral components within the interface circuit 21 a is described with reference to FIG. 10. The MUX/DEMUX 250 a includes a byte striping 251. The byte striping 251 distributes transmission data across Lane#0 to Lane#3. Note here that Lane#0 to Lane#3 are lane identification numbers used according to a communication protocol. For example, when a driver exercising control over the interface circuit 21 a makes a lane designation to the interface circuit 21 a, the driver uses the identification numbers, Lane#0 to Lane#3.

The switch 260 a includes input terminals 261 to 265 and output terminals 266 to 269. According to an instruction from the control circuit 220 a, the switch 260 a changes connection between the input terminals 261 to 265 and the output terminals 266 to 269. To the input terminal 261, a test signal from the pulse generator 240 a is input. To the input terminals 262 to 265, data output from Lane#0 to Lane#3, respectively, of the byte striping 251 is input. Signals output from the output terminals 266 to 269 are input to the transmitting/receiving units 210 a to 210 d, respectively.

FIG. 10 depicts connection status of the switch 260 a in the case where no diagnosis is being performed. In this status, the input terminals 262 to 265 are connected to the output terminals 266 to 269, respectively. In this case, data output from Lane#0 to Lane#3 of the byte striping 251 is output through the lanes 22 a to 22 d, respectively. In this status, communication is performed with the recognition of the lanes 22 a to 22 d as Lane#0 to Lane#3, respectively.

FIG. 11 is a second example of the switch connection status. FIG. 11 depicts connection status of the switch 260 a in the case where the control circuit 220 a has received an instruction of diagnosis on Lane#1. In this case, according to an instruction from the control circuit 220 a, the switch 260 a changes the connection of the output terminal 267 from the input terminal 263 to the input terminal 261. Herewith, it is possible to perform diagnosis on the lane 22 b by supplying a test signal from the pulse generator 240 a to the transmitting/receiving unit 210 b while continuing data communication by use of the lanes 22 a, 22 c, and 22 d.

In an actual process, the control circuit 220 a causes the interface circuit 21 a to enter a power saving state (the L0s state) with Lane#1 being idle from a normal operational state (“L0” state). This allows the interface circuit 21 a to continue communication by use of the remaining Lane#0, Lane#2, and Lane#3 without change of the communication protocol. Then, after the state transition is completed, the control circuit 220 a instructs the switch 260 a to change the connection of the output terminal 267 from the input terminal 263 to the input terminal 261. When the change is completed, the control circuit 220 a causes the pulse generator 240 a to output a test signal. Herewith, it is possible to perform diagnosis on the lane 22 b which has been associated with Lane#1 not currently in use for communication.

FIG. 12 is a third example of the switch connection status. FIG. 12 depicts connection status of the switch 260 a in the case where the control circuit 220 a has received an instruction of diagnosis on Lane#0. In this case, the diagnosis target lane is the lane 22 a associated with Lane#0. Note that, according to the PCIe standard, communication is not possible without using Lane#0 which is a main lane. Therefore, the control circuit 220 a instructs the switch 260 a to change the connection of Lane#0 from the diagnosis target lane 22 a to a different lane. Herewith, it is possible to perform diagnosis on the diagnosis target lane which was associated with Lane#0 until then while continuing communication on Lane#0.

Specifically, under the control of the control circuit 220 a, connection changes are made in such a manner to obtain, for example, the switch connection status illustrated in FIG. 12. First, the control circuit 220 a causes the interface circuit 21 a to enter the power saving state (the L0s state) with Lane#3 being idle so that Lane#3 is not used for communication. Then, the connection of the input terminal 262 connected to Lane#0 is changed from the output terminal 266 connected to the diagnosis target lane 22 a to a different output terminal (in this example, the output terminal 267). Along with this connection change, the connections of the input terminals 263 and 264 are also changed to the output terminals 268 and 269, respectively. Herewith, it is possible to continue communication with the recognition of lanes 22 b to 22 d as Lane#0 to Lane#2, respectively. Subsequently, the input terminal 261 is connected to the output terminal 266 so that a test signal output from the pulse generator 240 a is transmitted to the transmitting/receiving unit 210 a to perform diagnosis on the lane 22 a. Under the above-described control, it is possible to perform diagnosis on the diagnosis target lane which was previously associated with Lane#0 while continuing communication using Lane#0 without change of the communication protocol.

FIG. 13 is a block diagram illustrating a configuration example of processing functions of a controller module. The example of FIG. 13 depicts processing functions of the controller module 200 a. The controller module 200 a includes a diagnosis control unit 209 aa, an operation control unit 209 ab, and drivers 201 aa and 201 ab. The diagnosis control unit 209 aa and the operation control unit 209 ab are implemented by the FPGA 209 a, and the drivers 201 aa and 201 ab are implemented by the CPU 201 a. For example, in the case where the FPGA 209 a includes a processor 209 ac capable of executing programs, processes performed by the diagnosis control unit 209 aa and the operation control unit 209 ab are implemented by the processor 209 ac executing a predetermined firmware program. In addition, processes performed by the drivers 201 aa and 201 ab are implemented by the CPU 201 a executing a predetermined firmware program.

In addition, the flash memory 209 a 1 stores therein a diagnosis target channel table 270 and result management tables 280 as information referenced during the execution of processes by the FPGA 209 a. The diagnosis target channel table 270 registers information indicating interface circuits within the storage device 100 and the sequence of lane diagnosis. The result management tables 280 register diagnostic results for individual interface circuits and information indicating usage status of each lane. Note that one result management table 280 is created for each pair of interface circuits connected to each other via serial transmission paths.

The diagnosis control unit 209 aa determines diagnosis target interface circuits and lanes based on the diagnosis target channel table 270. The diagnosis control unit 209 aa instructs, via either the driver 201 aa or 201 ab, the diagnosis target interface circuits to start diagnosis with designation of the diagnosis target lanes. The operation control unit 209 ab receives a diagnostic result via either the driver 201 aa or 201 ab and registers the diagnostic result in the corresponding result management table 280. In addition, based on diagnostic results for the entire storage device 100, registered in the result management tables 280, the operation control unit 209 ab controls the use or non-use of individual lanes of each interface circuit via either the driver 201 aa or 201 ab.

The driver 201 aa controls communication and diagnostic operations in PCIe interfaces 21-1 a, 21-1 b, and so on amongst interface circuits within the storage device 100. As for the control of diagnostic operations, the driver 201 aa receives a diagnosis start instruction with designation of a diagnosis target lane from the diagnosis control unit 209 aa, and transmits the received instruction to a corresponding PCIe interface. In addition, the driver 201 aa transmits a diagnostic result received from a PCIe interface to the diagnosis control unit 209 aa. Further, the driver 201 aa controls the use or non-use of each lane of a PCIe interface according to an instruction from the operation control unit 209 ab. The driver 201 ab controls communication and diagnostic operations in SAS interfaces 21-2 a, 21-2 b, and so on amongst the interface circuits within the storage device 100. Because processes of the driver 201 ab are the same as those performed by the driver 201 aa on the PCIe interface 21-1 a, 21-1 b, and so on, repeated descriptions thereof are omitted.

Note that the controller module 200 b also has the same processing functions as those of the controller module 200 a of FIG. 13. As for the FPGA 209 a of the controller module 200 a and the FPGA 209 b of the controller module 200 b, for example, one of them operates as a master while the other operates as a slave. For example, if the FPGA 209 a operates as a master, the diagnosis control unit 209 aa and the operation control unit 209 ab lead the diagnostic operations and the control of the use or non-use of individual lanes of each interface circuit. In addition, in the case of transmitting an instruction to an interface circuit of the other controller module 200 b, for example, the instruction is transmitted from the FPGA 209 a to the FPGA 209 b and then transferred via a driver implemented by the CPU 201 b to the interface circuit of the controller module 200 b. In addition, information transmitted from an interface circuit to the FPGA 209 b, such as a diagnostic result, is transferred through a route reverse to the above-described one.

FIG. 14 illustrates an example of the diagnosis target channel table. The diagnosis target channel table 270 is stored in the flash memory 209 a 1. The diagnosis target channel table 270 is information by which the sequence of lanes to be diagnosed is identifiable. The diagnostic sequence is determined by the diagnosis control unit 209 aa of the FPGA 209 a in consideration of access performance from the host device 400 to the device enclosure 300. How to determine the diagnostic sequence is described in detail later. The diagnosis target channel table 270 includes columns named “group” and “diagnosis target channel”. Each field in the group column contains information for identifying a group. Each field in the diagnosis target channel column contains information on diagnosis target channel or channels.

Each diagnosis target channel corresponding to one group designates the location of a channel targeted for diagnosis by the names of individual devices each connected at either endpoint of the channel. Each field in the diagnosis target channel column contains at least one pair of the names of such devices. Each field in the diagnosis target channel column may also designate lane numbers indicating diagnosis targets on the corresponding channel. Each group registered in the diagnosis target channel table 270 is further divided into subgroups. For example, Group “1” is divided into Subgroups “1a” to “1d”. The subgroups correspond one-to-one with lanes included in each channel registered in the diagnosis target channel field of the corresponding group. The diagnosis control unit 209 aa determines lanes to be diagnosed with reference to the diagnosis target channel table 270. The diagnosis control unit 209 aa sequentially determines the lanes to be diagnosed, starting with Group “1”. In addition, the diagnosis control unit 209 aa sequentially determines the lanes to be diagnosed, starting with Subgroup “1a” of Group “1”.

For example, in the example of FIG. 14, “Lane#0 between CPU/CM#0 and IOC/CM#0” is registered in the diagnosis target channel field corresponding to Subgroup “1a”. This indicates that Lane#0 of the channel connecting the CPU 201 a and the IOC 205 a of CM#0 (the controller module 200 a) is designated as a diagnosis target. In this case, the diagnosis control unit 209 aa transmits diagnosis start instructions associated with Lane#0 to interface circuits each connected at either endpoint of the corresponding channel via a driver (in this case, the driver 201 aa). Each of the interface circuits performs diagnosis on the differential signal lines for transmission of Lane#0 and notifies the diagnosis control unit 209 aa of the diagnostic result via the driver 201 aa. In addition, in the example of FIG. 14, two channels “Lane#0 between CPU/CM#0 and IOC/CM#0” and “Lane#0 between IOC/CM#0 and SASExp/CM#0” (i.e., two lanes, each in a different channel) are registered in the diagnosis target channel field corresponding to Subgroup “1a”. In this case, the diagnosis control unit 209 aa performs diagnosis on the two channels in parallel.

FIG. 15 illustrates an example of the result management tables. Result management tables 280 a, 280 b, 280 c, and so on are stored in the flash memory 209 a 1. Each of the result management tables 280 a, 280 b, 280 c, and so on registers, with respect to each lane, a diagnostic result of a channel in a single direction between a pair of devices. For example, the result management table 280 a includes diagnostic results for individual lanes of the channel identified by “CPU/CM#0→PCH/CM#0”. That is, the result management table 280 a registers the diagnostic result of each lane in the channel for transmission from the CPU 201 a to the PCH 207 a.

Each field in a column named “diagnostic result” contains one of the following: normal; abnormality sign;

and abnormal. “Normal” indicates that the corresponding diagnosis target lane is normal. “Abnormality sign” indicates that an abnormality sign is present in the corresponding diagnosis target lane. “Abnormal” indicates that there is an abnormality in the corresponding diagnosis target lane. Further, each result management table registers a use flag and the times L3 and L4 with respect to each lane. Each field in the use flag column contains a flag indicating whether to use the corresponding lane (the lane to be enabled) or not to use the lane and shut it down. In the case of using the lane, “true” is registered. In the case of not using the lane, “false” is registered. The times L3 and L4 indicate the lower and upper limits, respectively, of the second normal range used in diagnosis to detect an abnormality sign.

A diagnostic process carried out at link-up is described next with reference to a flowchart. FIG. 16 is a flowchart illustrating an example of the diagnostic process at link-up. The process of FIG. 16 is described according to the step numbers in the flowchart.

[Step S11] Step S11 is executed, for example, when the interface circuit 21 a has started with the storage device 100 being powered on, or when the interface circuit 21 a has been reset and restarted. The control circuit 220 a of the interface circuit 21 a performs a process of detecting the rise time of a test signal with changing the diagnosis target lane.

Specifically, the control circuit 220 a determines a diagnosis target lane. The control circuit 220 a causes the switch 260 a to perform connection line switching so as to connect the input terminal 261 connected to the pulse generator 240 a to the output terminal connected to the diagnosis target lane. Then, the control circuit 220 a causes the pulse generator 240 a to transmit a test signal. The detection circuit 213 a detects the rise time of the test signal in the diagnosis target lane, and notifies the control circuit 220 a of the detected rise time. When detecting, based on the detected rise time, that the interface circuit 21 b has been connected at the other endpoint, the control circuit 220 a stores the detected rise time in the memory 230 a, in association with the number of the diagnosis target lane.

The interface circuit 21 a performs the above-described process on each of all the lanes of a port concerned, and detects the rise time for each lane and stores the detected rise time in the memory 230 a. Note that, in the case where the control circuit 220 a determines that an interface circuit is not connected at the other endpoint, step S12 and the subsequent steps are not executed.

[Step S12] The control circuit 220 a of the interface circuit 21 a transmits diagnosis start notification to the CPU 201 a.

[Step S13] A driver (the driver 201 aa, for example) of the CPU 201 a transmits the diagnosis start notification to the FPGA 209 a.

[Step S14] The diagnosis control unit 209 aa of the FPGA 209 a refers to the flash memory 209 a 1 to determine whether information on the second normal range (i.e., the times L3 and L4) corresponding to the interface circuit 21 a, which is the source of the diagnosis start notification (hereinafter simply referred to as the “notification-source interface circuit 21 a”), is stored. This determination is made, for example, by checking whether the result management table 280 corresponding to the notification-source interface circuit 21 a is stored in the flash memory 209 a 1. When the corresponding result management table 280 is stored, the second normal range information is found in the stored result management table 280. If the result management table 280 is stored, the diagnosis control unit 209 aa moves to step S15. If not, the diagnosis control unit 209 aa moves to step S16.

Note here that, for example, if the notification-source interface circuit 21 a is newly installed, no second normal range information corresponding to the interface circuit 21 a is found. Also if an interface circuit installed at the same location has been replaced with the notification-source interface circuit 21 a, no second normal range information corresponding to the interface circuit 21 a is found.

[Step S15] The diagnosis control unit 209 aa acquires the second normal range information (the times L3 and L4) for each lane from the result management table 280 referenced in step S14. The diagnosis control unit 209 aa transmits, to the CPU 201 a, the second normal range information together with an abnormality sign diagnosis start instruction, and instructs the CPU 201 a to transmit the information with the instruction to the notification-source interface circuit 21 a.

[Step S16] The diagnosis control unit 209 aa acquires information on the first normal range (the times L1 and L2) pre-stored in the flash memory 209 a 1. The diagnosis control unit 209 aa transmits, to the CPU 201 a, the first normal range information together with an abnormality diagnosis start instruction, and instructs the CPU 201 a to transmit the information with the instruction to the notification-source interface circuit 21 a.

Note that, because the times L1 and L2 indicating the first normal range are fixed values, they need not be pre-stored in the memory 230 a. If this is the case, the first normal range information need not be transmitted in step S16.

[Step S17] The diagnosis control unit 209 aa updates the diagnosis target channel table 270 in response to the interface circuit 21 a being newly installed. Specifically, the diagnosis control unit 209 aa updates the diagnosis target channel table 270 according to the following rules (1) to (3) in consideration of access performance from the host device 400 to the device enclosure 300. Note that the order of priority is (1)>(2)>(3).

(1) The diagnosis control unit 209 aa determines locations of channels to be diagnosed at the same time in such a manner that no significant difference arises in the data flow rate between the upstream and the downstream. For example, the lane count at the upstream of the IOC 205 a, i.e., the number of lanes between the CPU 201 a and the IOC 205 a, is 8. On the other hand, the lane count between the IOC 205 a and the SAS expander 206 a is 4, and the lane count between the IOC 205 a and the SAS expander 206 b is 4. Therefore, the total lane count at the downstream of the IOC 205 a is 8. In this case, because the upstream lane count and the downstream lane count are the same, there is no difference in the data flow rate between the upstream and the downstream even when one lane each at both the upstream and the downstream undergoes diagnosis. Therefore, the diagnosis control unit 209 aa registers, for example, four lanes between the CPU 201 a and the IOC 205 a and the four lanes between the IOC 205 a and the SAS expander 206 a as a single group to be diagnosed at the same time. In addition, the diagnosis control unit 209 aa registers the remaining four lanes between the CPU 201 a and the IOC 205 a and the four lanes between the IOC 205 a and the SAS expander 206 b as a different single group to be diagnosed at the same time. Thus, selecting diagnosis target lanes in such a manner that there is little difference in the data flow rate between the upstream and the downstream decreases the possibility that communication will become stagnant in some parts within the storage device 100, which will result in decreased access performance to the device enclosure 300.

Note that, in the example above, the combination of lanes to be diagnosed at the same time is determined in such a manner that the number of lanes used for communication between the CPU 201 a and the IOC 205 a is the same as the number of lanes used for communication between the IOC 205 a and the SAS expander 206 a or 206 b. However, as another example, this combination may be determined in such a manner that a difference between the number of lanes used for communication between the CPU 201 a and the IOC 205 a and the number of lanes used for communication between the IOC 205 a and the SAS expander 206 a or 206 b is equal to or less than a certain value. Alternatively, this combination may be determined in such a manner that the ratio of the number of lanes used for communication between the CPU 201 a and the IOC 205 a to the number of lanes used for communication between the IOC 205 a and the SAS expander 206 a or 206 b falls within a certain range.

(2) The diagnosis control unit 209 aa makes the grouping in such a manner that diagnosis is performed on a large number of lanes at the same time provided that the impact on access performance to the device enclosure 300 is kept small. For example, the lane counts at the upstream and downstream of the IOC 205 a are both 8, as mentioned above, which are relatively large numbers. Therefore, setting one lane each at the upstream and downstream as diagnosis targets causes a relatively small decrease in access performance to the device enclosure 300. In view of this, the diagnosis control unit 209 aa sets a group in such a manner that one lane each at the upstream and downstream of the IOC 205 a undergo diagnosis at the same time.

(3) The diagnosis control unit 209 aa determines the sequence of lane diagnosis in such a manner as to preferentially diagnose channels in the controller module 200 a and subsequently diagnose channels in the controller module 200 b. This allows, even during the diagnosis, one of the controller modules 200 a and 200 b to operate while maintaining access performance.

In addition to updating the diagnosis target channel table 270 described above, the diagnosis control unit 209 aa also creates the result management table 280 corresponding to the newly installed interface circuit 21 a and stores it in the flash memory 209 a 1.

[Step S18] The driver 201 aa of the CPU 201 a transmits the information received from the FPGA 209 a in step S15 or S16 to the interface circuit 21 a.

[Step S19] The control circuit 220 a of the interface circuit 21 a stores, in the memory 230 a, the first or second normal range information received from the CPU 201 a. In the case of receiving an abnormality diagnosis start instruction, the control circuit 220 a determines, with respect to each of the diagnosis target lanes, whether the rise time detected in step S11 falls within the received first normal range, to thereby determine the presence or absence of an abnormality in the lane. Herewith, abnormality diagnosis for each lane is performed. On the other hand, in the case of receiving an abnormality sign diagnosis start instruction, the control circuit 220 a determines, with respect to each of the diagnosis target lanes, whether the rise time detected in step S11 falls within the received second normal range, to thereby determine the presence or absence of an abnormality sign in the lane. Herewith, abnormality sign diagnosis for each lane is performed. The control circuit 220 a transmits diagnostic results to the CPU 201 a.

[Step S20] The driver 201 aa of the CPU 201 a transmits the received diagnostic results to the FPGA 209 a.

[Step S21] The operation control unit 209 ab of the FPGA 209 a carries out a diagnostic result receiving process. In this process, the operation control unit 209 ab registers the received diagnostic results in the result management table 280 corresponding to the interface circuit 21 a, which is the source of the diagnostic results. In addition, if an abnormality has been detected in one or more lanes, the operation control unit 209 ab carries out an abnormality handling process to control which lanes of the interface circuit 21 a to be used and which lanes to be shut down. Note that the diagnostic result receiving process is described in detail later with reference to FIG. 19.

FIG. 17 is a first flowchart illustrating an example of the determining process. The process of FIG. 17 corresponds to step S19 of FIG. 16. The process of FIG. 17 is described according to the step numbers in the flowchart.

[Step S31] The control circuit 220 a selects one diagnosis target lane amongst a plurality of lanes of the port. The control circuit 220 a acquires the rise time detected for the diagnosis target lane from the memory 230 a.

[Step S32] The control circuit 220 a determines whether to have acquired the second normal range information from the FPGA 209 a. If having acquired the second normal range information, the control circuit 220 a moves to step S41. If having acquired no second normal range information (that is, if having received the first normal range information), the control circuit 220 a moves to step S33.

[Step S33] The control circuit 220 a determines whether the rise time acquired in step S31 falls outside the first normal range notified by the FPGA 209 a. If the rise time falls outside the first normal range, the control circuit 220 a moves to step S34. If the rise time falls within the first normal range, the control circuit 220 a moves to step S35.

[Step S34] The control circuit 220 a notifies the CPU 201 a that there is an abnormality in the diagnosis target lane. Then, the control circuit 220 a moves to step S39.

Upon receiving the notification, the CPU 201 a notifies the FPGA 209 a that there is an abnormality in the diagnosis target lane.

[Step S35] According to an instruction from the control circuit 220 a, the transmitting/receiving unit 210 establishes a link between transmission (Tx) and reception (Rx) of the diagnosis target lane.

[Step S36] The control circuit 220 a determines the second normal range based on the rise time by the procedure described in FIG. 9.

[Step S37] The control circuit 220 a notifies the CPU 201 a that the diagnosis target lane is normal. Upon receiving the notification, the CPU 201 a notifies the FPGA 209 a that the diagnosis target lane is normal.

[Step S38] The control circuit 220 a transmits the second normal range information (the times L3 and L4) to the CPU 201 a. The CPU 201 a notifies the FPGA 209 a of the second normal range information.

[Step S39] The control circuit 220 a determines whether all lanes of the port have undergone diagnosis. If all the lanes have undergone diagnosis, the determining process ends. If one or more lanes of the port remain undiagnosed, the control circuit 220 a moves to step S31.

FIG. 18 is a second flowchart illustrating the example of the determining process. The process of FIG. 18 is described according to the step numbers in the flowchart.

[Step S41] The control circuit 220 a determines whether the rise time acquired in step S31 falls outside the second normal range notified by the FPGA 209 a. If the rise time falls outside the second normal range, the control circuit 220 a moves to step S42. If the rise time falls within the second normal range, the control circuit 220 a moves to step S43.

[Step S42] The control circuit 220 a notifies the CPU 201 a that an abnormality sign is present in the diagnosis target lane. Then, the control circuit 220 a moves to step S39. Upon receiving the notification, the CPU 201 a notifies the FPGA 209 a that an abnormality sign is present in the diagnosis target lane.

[Step S43] According to an instruction from the control circuit 220 a, the transmitting/receiving unit 210 establishes a link between Tx and Rx of the diagnosis target lane.

[Step S44] The control circuit 220 a notifies the CPU 201 a that the diagnosis target lane is normal. Then, the control circuit 220 a moves to step S39. Upon receiving the notification, the CPU 201 a notifies the FPGA 209 a that the diagnosis target lane is normal.

Thus, the interface circuit 21 a is able to detect lanes with an abnormality or abnormality sign in the diagnostic process at link-up.

FIG. 19 is a flowchart illustrating an example of the diagnostic result receiving process. The process of

FIG. 19 corresponds to step S21 of FIG. 16. The process of FIG. 19 is described according to the step numbers in the flowchart.

[Step S51] The operation control unit 209 ab of the FPGA 209 a receives, from the CPU 201 a, diagnostic results of the individual lanes of the interface circuit 21 a. In addition to the diagnostic results, the operation control unit 209 ab may also receive the second normal range information for each lane.

[Step S52] The operation control unit 209 ab registers the diagnostic results of the individual lanes in the result management table 280 corresponding to the interface circuit 21 a which conducted the diagnosis.

[Step S53] The operation control unit 209 ab determines whether the diagnostic results of all the lanes are “normal”. If there is a lane whose diagnostic result is “abnormal”, the operation control unit 209 ab moves to step S54. On the other hand, if the diagnostic results of all the lanes are “normal”, the operation control unit 209 ab registers, within the result management table 280, “true” in the use flag field corresponding to each of the lanes. In addition, in the case of having received the second normal range information of the individual lanes, the operation control unit 209 ab registers, within the result management table 280, the information in the times L3 and L4 field corresponding to each of the lanes. Then, the operation control unit 209 ab ends the diagnostic result receiving process.

[Step S54] The operation control unit 209 ab carries out an abnormality handling process. This process is described in detail later with reference to FIGS. 23 and 24.

Note that, after step S51 or S52, for example, the operation control unit 209 ab may instruct the CPU 201 a to notify an external device (for example, the host device 400 or a management terminal of the storage device 100) of the diagnostic results. In this case, upon receiving the instruction, the CPU 201 a causes the external device to display, for example, display information representing diagnostic content. Herewith, by visually perceiving the display information, the user is able to understand whether an abnormality or abnormality sign has been detected, and if so, which lane of which device the abnormality or abnormality sign has been detected from.

Next described is the diagnostic process during normal operation, with reference to sequence diagrams and a flowchart. Normal operation is a condition where access processing to the device enclosure 300 according to a request from the host device 400 is in progress within the storage device 100. FIG. 20 is a first sequence diagram illustrating an example of a diagnosis control process during normal operation. The process of FIG. 20 is described according to the step numbers in the flowchart.

[Step ST100] The diagnosis control unit 209 aa of the FPGA 209 a determines a diagnosis target lane with reference to the diagnosis target channel table 270. Assume here that one lane included in the channel between the interface circuits 21 a and 21 b is determined as the diagnosis target lane.

[Step ST101] The diagnosis control unit 209 aa of the FPGA 209 a transmits, to the CPU 201 a, a diagnosis start instruction for the diagnosis target lane. This diagnosis start instruction includes identification information of a device connected at one endpoint of the diagnosis target lane or the interface circuit 21 a and the number of the diagnosis target lane.

[Step ST102] The diagnosis control unit 209 aa of the FPGA 209 a transmits, to the CPU 201 a, a diagnosis start instruction for the diagnosis target lane. This diagnosis start instruction includes identification information of a device connected at the other endpoint of the diagnosis target lane or the interface circuit 21 b and the number of the diagnosis target lane. Note that the number of the diagnosis target lane is the same as that in step ST101.

Steps ST101 and ST102 above are executed each time the diagnosis control unit 209 aa selects a subgroup in the diagnosis target channel table 270 sequentially from the top. In this regard, in the case where a plurality of lanes are registered in the selected subgroup, steps ST101 and ST102 and the subsequent steps are executed for each of the registered lanes. This enables parallel diagnosis on the registered lanes.

[Step ST103] A driver (the driver 201 aa, for example) of the CPU 201 a transmits a diagnosis start instruction to the interface circuit 21 a, which is designated in the diagnosis start instruction transmitted in step ST101. This diagnosis start instruction includes the number of the diagnosis target lane.

[Step ST104] The driver 201 aa of the CPU 201 a transmits a diagnosis start instruction to the interface circuit 21 b, which is designated in the diagnosis start instruction transmitted in step ST102. This diagnosis start instruction includes the number of the diagnosis target lane.

[Step ST105] The interface circuit 21 a transmits diagnosis start notification to the interface circuit 21 b.

[Step ST106] The interface circuit 21 b transmits diagnosis start acceptance notification to the interface circuit 21 a.

[Step ST107] The interface circuit 21 a enters the power saving state (the L0s state) with the diagnosis target lane being idle. Note that in the case where the main lane (Lane#0) is designated as the diagnosis target lane, the interface circuit 21 a causes a predetermined lane (Lane#3 in the example of FIG. 12) other than Lane#0 to go idle.

[Step ST108] The interface circuit 21 a transmits, to the interface circuit 21 b, transition completion notification indicating the completion of the transition to the power saving state. Note that in the case where Lane#0 is designated as the diagnosis target lane, a predetermined lane other than Lane#0 is brought to idle, as in step ST107.

[Step ST109] The interface circuit 21 b enters the power saving state (the L0s state) with the diagnosis target lane being idle.

[Step ST110] The interface circuit 21 b transmits, to the interface circuit 21 a, transition completion notification indicating the completion of the transition to the power saving state.

[Step ST111] The interface circuit 21 a performs abnormality sign diagnosis on the diagnosis target lane.

[Step ST112] The interface circuit 21 b performs abnormality sign diagnosis on the diagnosis target lane.

FIG. 21 is a second sequence diagram illustrating the example of the diagnosis control process during normal operation. The process of FIG. 21 is described according to the step numbers in the flowchart.

[Step ST121] After completing the diagnosis of the diagnosis target lane, the interface circuit 21 a transmits diagnosis completion notification to the interface circuit 21 b.

[Step ST122] After completing the diagnosis of the diagnosis target lane, the interface circuit 21 b transmits diagnosis completion notification to the interface circuit 21 a.

[Step ST123] After completing the transmission process in step ST121 and a receiving process of the information transmitted in step ST122, the interface circuit 21 a exits the power saving state and enters the normal operational state (the L0 state).

[Step ST124] The interface circuit 21 a transmits, to the interface circuit 21 b, transition completion notification indicating the completion of the transition to the normal operational state.

[Step ST125] After completing a receiving process of the information transmitted in step ST121 and the transmission process in step ST122, the interface circuit 21 b exits the power saving state and enters the normal operational state (the L0 state).

[Step ST126] The interface circuit 21 b transmits, to the interface circuit 21 a, transition completion notification indicating the completion of the transition to the normal operational state. In response to the transmission of the transition completion notification, the interface circuit 21 b resumes communication with all the lanes being used prior to the start of the diagnosis, including the diagnosis target lane. In like fashion, in response to the reception of the transition completion notification, the interface circuit 21 a resumes communication with all the lanes being used prior to the start of the diagnosis.

[Step ST127] The interface circuit 21 a transmits the diagnostic result to the CPU 201 a.

[Step ST128] The CPU 201 a transmits, to the FPGA 209 a, the diagnostic result transmitted in step ST127. The diagnosis control unit 209 aa of the FPGA 209 a identifies the result management table 280 corresponding to the channel extending from the interface circuit 21 a to the interface circuit 21 b. The diagnosis control unit 209 aa updates, within the identified result management table 280, a diagnosis result associated with the diagnosis target lane with the diagnostic result received from the CPU 201 a.

[Step ST129] The interface circuit 21 b transmits the diagnostic result to the CPU 201 a.

[Step ST130] The CPU 201 a transmits, to the FPGA 209 a, the diagnostic result transmitted in step ST129. The diagnosis control unit 209 aa of the FPGA 209 a identifies the result management table 280 corresponding to the channel extending from the interface circuit 21 b to the interface circuit 21 a. The diagnosis control unit 209 aa updates, within the identified result management table 280, a diagnosis result associated with the diagnosis target lane with the diagnostic result received from the CPU 201 a.

Note that, when receiving the diagnostic result in steps ST128 and ST130, the diagnosis control unit 209 aa may instruct the CPU 201 a to notify an external device (for example, the host device 400 or a management terminal of the storage device 100) of the diagnostic result. In this case, upon receiving the instruction, the CPU 201 a causes the external device to display, for example, display information representing diagnostic content. Herewith, by visually perceiving the display information, the user is able to understand whether an abnormality sign has been detected, and if so, which lane of which device the abnormality sign has been detected from.

[Step ST131] When an abnormality sign has been determined to be present in the diagnosis target lane, the operation control unit 209 ab of the FPGA 209 a carries out the abnormality handling process. The abnormality handling process is described in detail later with reference to FIGS. 23 and 24.

According to the process of FIGS. 20 and 21 above, steps ST105 and ST106 allow the start of the diagnosis at each of the interface circuits 21 a and 21 b to synchronize. Then, steps ST121 and ST122 allow the end of the diagnosis at each of the interface circuits 21 a and 21 b to synchronize. Because bidirectional communication takes place between the interface circuits 21 a and 21 b, a communication error may occur if diagnosis is performed only in one direction. The occurrence of such a communication error is prevented by synchronizing the start and end of the diagnosis between the interface circuits 21 a and 21 b, as described above.

FIG. 22 is a flowchart illustrating an example of a diagnostic process performed by each interface circuit during normal operation. The process of FIG. 22 corresponds to that performed by the interface circuit 21 a in step ST111 of FIG. 20. Note that, also in step ST112 of FIG. 20, a similar process to that of FIG. 22 is performed by the interface circuit 21 b. The process of FIG. 22 is described according to the step numbers in the flowchart.

[Step S61] The control circuit 220 a instructs the switch 260 a to implement a connection switch in such a manner that the designated diagnosis target lane is connected to the pulse generator 240 a. According to the instruction, the switch 260 a changes connections within the switch 260 a. In this regard, communication with the interface circuit 21 b is continued using, amongst lanes being used prior to the start of the diagnosis, lanes except for the diagnosis target lane.

Note here that a lane actually diagnosed in the channel is one associated with the number of the diagnosis target lane designated by the diagnosis control unit 209 aa of the FPGA 209 a via the driver 201 aa of the CPU 201 a. For example, according to the configurations of FIGS. 10 to 13, the lane 22 a is diagnosed when Lane#0 is designated as a diagnosis target lane, and the lane 22 b is diagnosed when Lane#1 is designated as a diagnosis target lane.

In step S61, when a lane other than Lane#0 is designated as a diagnosis target lane, only the connection of the lane to be actually diagnosed is changed within the switch 260 a, as illustrated in FIG. 11. On the other hand, when Lane#0 is designated as a diagnosis target lane, connections within the switch 260 a are changed in such a manner that a different lane on the channel is reconnected to Lane#0, as illustrated in FIG. 12. Note that, in the case where Lane#0 is designated as a diagnosis target lane, in step ST107 of FIG. 20, the control circuit 220 a causes not Lane#0 but a lane amongst the remaining lanes, whose connection with a lane on the channel is disconnected (Lane#3 in the example of FIG. 12), to go idle.

[Step S62] The control circuit 220 a instructs the pulse generator 240 a to output a test signal. According to the instruction, the pulse generator 240 a transmits a test signal. Herewith, the test signal is transmitted to the differential signal lines of the diagnosis target lane in the channel. The detection circuit 213 a detects the rise time of the voltage in the differential signal lines, and notifies the control circuit 220 a of the detected rise time.

[Step S63] The control circuit 220 a acquires, from the memory 230 a, the second normal range information (the times L3 and L4) corresponding to the diagnosis target lane. The control circuit 220 a determines whether the detected rise time falls outside the second normal range. If the rise time falls outside the second normal range, the control circuit 220 a moves to step S64. If the rise time falls within the second normal range, the control circuit 220 a moves to step S65.

[Step S64] The control circuit 220 a determines that an abnormality sign is present in the diagnosis target lane. Then, the control circuit 220 a moves to step S66.

[Step S65] The control circuit 220 a determines that the diagnosis target lane is normal.

[Step S66] The control circuit 220 a instructs the switch 260 a to restore the connection status to its former state prior to the execution of step S61. According to the instruction, the switch 260 a changes connections within the switch 260 a. Subsequently, the diagnostic process ends.

Thus, using the second normal range information, the control circuit 220 a is able to determine whether an abnormality sign is present in the diagnosis target lane.

Next described is the abnormality handling process. FIG. 23 is a first flowchart illustrating an example of the abnormality handling process. The process of FIG. 23 corresponds to that performed by the operation control unit 209 ab of the FPGA 209 a in step S54 of FIG. 19 or step ST131 of FIG. 21. In addition, the process of FIG. 23 is executed for each diagnosis target lane in which an abnormality or abnormality sign has been detected within the same port. The process of FIG. 23 is described according to the step numbers in the flowchart.

[Step S71] The operation control unit 209 ab determines whether two or more lanes are in use within the port to which the diagnosis target lane belongs. The lanes in use are lanes whose use flag in the result management table 280 is set to “true”. If two or more lanes are in use, the process moves to step S72. If there are not two or more lanes in use, the process moves to step S75.

[Step S72] The operation control unit 209 ab determines whether the diagnostic result of the diagnosis target lane is “abnormal”. If the diagnostic result is “abnormal”, the process moves to step S73. If the diagnostic result is not “abnormal” (i.e., an abnormality sign has been detected), the process moves to step S77.

[Step S73] The operation control unit 209 ab determines whether, within the port to which the diagnosis target lane belongs, there is an abnormality sign lane, the use of which is prohibited. The lane the use of which is prohibited is a lane whose use flag in the result management table 280 is set to “false”. The abnormality sign lane is a lane whose diagnostic result in the result management table 280 is “abnormality sign”. If there is an abnormality sign lane the use of which is prohibited, the process moves to step S74. If there is no such abnormality sign lane, the process moves to step S81.

[Step S74] The operation control unit 209 ab selects one of abnormality sign lanes in the port to which the diagnosis target lane belongs, and removes a prohibition on the use of the selected lane. That is, the operation control unit 209 ab registers, within the result management table 280, “true” in the use flag field corresponding to the selected lane. The operation control unit 209 ab moves to step S81.

[Step S75] The operation control unit 209 ab determines whether the diagnostic result of the diagnosis target lane is “abnormal”. If the diagnostic result is “abnormal”, the process moves to step S76. If the diagnostic result is not “abnormal” (i.e., an abnormality sign has been detected), the process moves to step S79.

[Step S76] The operation control unit 209 ab prohibits the use of the diagnosis target lane. That is, the operation control unit 209 ab registers, within the result management table 280, “false” in the use flag field corresponding to the diagnosis target lane. Then, the process moves to step S82.

[Step S77] The operation control unit 209 ab determines whether there is an abnormal lane, the use of which is prohibited, within the port to which the diagnosis target lane belongs. The abnormal lane is a lane whose diagnostic result in the result management table 280 is “abnormal”. If there is an abnormal lane the use of which is prohibited, the process moves to step S79. If there is no such abnormal lane, the process moves to step S78.

[Step S78] The operation control unit 209 ab determines whether, within the port to which the diagnosis target lane belongs, there is an abnormality sign lane, the use of which is prohibited. If there is an abnormality sign lane the use of which is prohibited, the process moves to step S79. If there is no such abnormality sign lane, the process moves to step S81.

[Step S79] The operation control unit 209 ab continues the use of the diagnosis target lane. That is, the operation control unit 209 ab registers, within the result management table 280, “true” in the use flag field corresponding to the diagnosis target lane. Then, the process moves to step S82.

FIG. 24 is a second flowchart illustrating the example of the abnormality handling process. The process of FIG. 24 is described according to the step numbers in the flowchart.

[Step S81] The operation control unit 209 ab prohibits the use of the diagnosis target lane. That is, the operation control unit 209 ab registers, within the result management table 280, “false” in the use flag field corresponding to the diagnosis target lane. In this case, because there is one or more lanes in use within the same port, the operation is continued using these other lanes.

[Step S82] The operation control unit 209 ab determines whether all lanes within the port have undergone diagnosis. If one or more lanes remain undiagnosed, the process ends. If all the lanes within the port have undergone diagnosis, the process moves to step S83.

[Step S83] The operation control unit 209 ab reflects changes in the lane usage conditions within the port in the interface circuits 21 a and 21 b. Specifically, the operation control unit 209 ab identifies one or more lanes whose use flag in the result management table 280 has been changed. The operation control unit 209 ab instructs the CPU 201 a to resume, amongst the identified lanes, each lane whose use flag is set to “true” and shut down each lane whose use flag is set to “false”. According to the instruction, the driver 201 aa of the CPU 201 a changes the lane usage conditions in the interface circuits 21 a and 21 b.

Note that, in step S83, the operation control unit 209 ab may instruct the CPU 201 a to notify an external device (for example, the host device 400 or a management terminal of the storage device 100) of the lane usage condition changes. In this case, upon receiving the instruction, the CPU 201 a causes the external device to display, for example, display information representing the changes.

According to the process of FIGS. 23 and 24 above, lanes in which an abnormality or abnormality sign has not been detected are continued to be used. On the other hand, each lane in which an abnormality has been detected is shut down. In addition, a lane in which an abnormality sign has been detected is used only if, amongst the remaining lanes, there is a lane having been shut down due to detection of an abnormality. Thus, a lane with an abnormality sign detected is used only under the limited conditions, which reduces the probability of a communication disconnection attributed to aging degradation of capacitors while maintaining communication performance at the highest possible level. In the case of continuing the use of a lane with an abnormality sign detected, the operation control unit 209 ab may instruct the interface circuit 21 a via the CPU 201 a to give reduced usage priority to the lane. Herewith, the probability of a communication disconnection in the lane is further reduced.

Note that, in response to an instruction to shut down the main lane (Lane#0), connections within the switch 260 a are changed in the interface circuit 21 a in such a manner that a different lane on the channel is reconnected to Lane#0, as illustrated in FIG. 12. That is, the connections within the switch 260 a are changed in such a manner that the input terminals 262, 263, and 264 are connected to the output terminals 267, 268, and 269, respectively, while the output terminal 266 is left unconnected to any input terminal. This allows the use of the lane 22 a with an abnormality or abnormality sign detected to be avoided while maintaining the use of Lane#0.

Next described is a process performed in the case where a port concerned has a low number of lanes. In an interface circuit, during diagnosis on a diagnosis target lane, communication is carried out by the remaining lanes of a port to which the diagnosis target lane belongs. The communication is thus continued by a smaller number of lanes than before the start of the diagnosis, which results in increased communication load on these lanes. As a result, communication timeouts tend to take place and large response delays may be observed. In view of these problems, a diagnosis control process illustrated in FIG. 25 next is performed in the case where a port has a small number of lanes.

FIG. 25 is a sequence diagram illustrating an example of a diagnostic process performed when a port has a small number of lanes. In FIG. 25, the same step numbers are given to steps with processing details that are common to those of FIG. 20. Assume in the example of FIG. 25 that the channel between the IOC 205 a and the SAS expander 206 a is designated as a diagnosis target. Assume also that the interface circuit 21 a of FIG. 20 is a SAS interface connected to one endpoint of the diagnosis target channel, on the IOC 205 a side. Assume also that the interface circuit 21 b of FIG. 20 is a SAS interface connected to the other endpoint of the diagnosis target channel, on the SAS expander 206 a side. Note that processes of the CPU 201 a are here implemented by the SAS-interface driver 201 ab. First, step ST100 a is executed in place of step ST100 of FIG. 20.

[Step ST100 a] The diagnosis control unit 209 aa of the FPGA 209 a determines a diagnosis target lane with reference to the diagnosis target channel table 270, as in step ST100. In addition, the diagnosis control unit 209 aa references the diagnosis target channel table 270 or the result management table 280 corresponding to a channel including the diagnosis target lane, to thereby identify the lane count of a port to which the diagnosis target lane belongs. Assume here that the diagnosis control unit 209 aa determines that the lane count is low. For example, when the lane count of a port is 4 or less, it is determined to be low.

When the lane count is determined not to be low, step ST101 and the subsequent steps of FIG. 20 are executed. On the other hand, if the lane count is determined to be low, the following steps ST100 b to ST100 j are executed before step ST101 of FIG. 20.

[Step ST100 b] The diagnosis control unit 209 aa of the FPGA 209 a transmits, to the CPU 201 a, an instruction to extend a timeout period (hereinafter simply referred to as the “timeout extension instruction”), addressed to the interface circuit 21 a connected to one endpoint of the diagnosis target channel.

[Step ST100 c] The driver 201 ab of the CPU 201 a transmits the timeout extension instruction to the interface circuit 21 a. The interface circuit 21 a performs a setting process to extend the timeout period and transmits extension completion notification to the CPU 201 a.

[Step ST100 d] The driver 201 ab of the CPU 201 a transmits the extension completion notification to the FPGA 209 a.

[Step ST100 e] The diagnosis control unit 209 aa of the FPGA 209 a transmits, to the CPU 201 a, a timeout extension instruction addressed to the interface circuit 21 b connected to the other endpoint of the diagnosis target channel.

[Step ST100 f] The driver 201 ab of the CPU 201 a transmits the timeout extension instruction to the interface circuit 21 b. The interface circuit 21 b performs a setting process to extend the timeout period and transmits extension completion notification to the CPU 201 a.

[Step ST100 g] The driver 201 ab transmits the extension completion notification to the FPGA 209 a.

[Step ST100 h] The diagnosis control unit 209 aa of the FPGA 209 a transmits, to the CPU 201 a, an input/output (IO) load adjustment instruction addressed to a device equipped with the interface circuit 21 a, connected at the upstream of the diagnosis target channel, that is the IOC 205 a. The IO load adjustment instruction instructs the IOC 205 a to decrease the ratio of transmission data distributed to the SAS expander 206 a and increase the ratio of transmission data distributed to the SAS expander 206 b.

[Step ST100 i] The driver 201 ab of the CPU 201 a transmits the IO load adjustment instruction to the IOC 205 a. According to the instruction, the IOC 205 a changes the data distribution ratio for both the SAS expanders 206 a and 206 b, and then transmits adjustment completion notification to the CPU 201 a.

[Step ST100 j] The driver 201 ab of the CPU 201 a transmits the adjustment completion notification to the FPGA 209 a.

Upon receiving the adjustment completion notification, the diagnosis control unit 209 aa of the FPGA 209 a performs steps ST101 and ST102 of FIG. 20. From this point forward, the same processing described in FIG. 20 is performed.

Although no illustrative figure is given here, upon receiving the diagnostic results transmitted in steps ST128 and ST130 of FIG. 21, the diagnosis control unit 209 aa of the FPGA 209 a transmits instructions to reverse the instructions issued in steps ST100 b, ST100 e, and ST100 h to the corresponding individual components via the CPU 201 a.

According to the process of FIG. 25 above, it is possible to decrease the likelihood of communication interruption between the interface circuits 21 a and 21 b due to a timeout during diagnosis. In addition, the amount of data transmitted from the IOC 205 a to the device enclosure 300 via the SAS expander 206 a is reduced. This decreases the likelihood of decreased access performance from the host device 400 to the device enclosure 300 due to communication failure between the interface circuits 21 a and 21 b acting as a bottleneck.

Note that, between steps ST100 b to ST100 g and steps ST100 h to ST100 j, only one of them may be executed. In addition, the processing of steps ST100 h to ST100 j is applicable to the case where a communication channel from the CPU 201 a or 201 b to the device enclosure 300 branches along the way and diagnosis is performed by interface circuits located on the branched communication channels after the branch point.

(c) Third Embodiment

Next described is a case where each of PCIe buses,

PCIe cables, and SAS cables is provided with an auxiliary lane. FIG. 26 illustrates an example of lane counts in a storage device according to a third embodiment. The storage device of the third embodiment differs from that of the second embodiment only in the connection lane counts between interface circuits, as illustrated in FIG. 26. Specifically, an auxiliary lane used for communication during diagnosis is added to each channel between interface circuits. For example, a total of five lanes are connected between the CPU 201 a and the PCIe switch 203 a after an auxiliary lane is added thereto.

FIG. 27 illustrates an example of an internal configuration of an interface circuit according to the third embodiment. According to the third embodiment, the interface circuit 21 a of FIGS. 10 to 12 is modified as an interface circuit 21 a 1 of FIG. 27. The interface circuit 21 a 1 is connected to an other endpoint interface circuit by lanes 22 a to 22 e. Amongst the lanes 22 a to 22 e, the lane 22 e is set as an auxiliary lane. The interface circuit 21 a 1 further includes a transmitting/receiving unit 210 e for signal transmission and reception via the lane 22 e. A switch 260 a 1 of the interface circuit 21 a 1 is different from the switch 260 a of FIGS. 10 to 12 in further having an output terminal 269 a used to connect to the transmitting/receiving unit 210 e.

When no diagnosis is being performed, the input terminals 262 to 265 are connected to the output terminals 266 to 269, respectively, as in the case of FIG. 10. Then, in the case where diagnosis on Lane#1 is instructed, for example, the connection of the input terminal 263 is changed from the output terminal 267 to the output terminal 269 a, and the input terminal 261 is then connected to the output terminal 267, as illustrated in FIG. 27. In this status, the transmitting/receiving unit 210 b performs diagnosis on the lane 22 b. At the same time, communication with the other endpoint interface circuit is continued using the lanes 22 a and 22 c to 22 e. According to this configuration, the number of lanes used to communicate with the other endpoint interface circuit remains the same as before the start of the diagnosis. This prevents a decrease in communication speed and communication interruption due to a timeout caused by increased communication load between the interface circuit 21 a 1 and the other endpoint interface circuit.

In addition, according to the above-described configuration, because the number of lanes used remains the same during and not during diagnosis, there is no need to determine locations of channels to be diagnosed at the same time in consideration of access performance from the host device 400 to the device enclosure 300, which is described in relation to step S17 of FIG. 16. Further, this eliminates the need for the extension of the timeout period and the IO load adjustment illustrated in FIG. 25. As a result, it is possible to simplify the diagnosis control procedures without a decrease in access performance from the host device 400 to the device enclosure 300 and partial communication breakdown.

According to one aspect, it is possible to perform diagnosis of a communication abnormality sign while continuing data communication.

All examples and conditional language provided herein are intended for the pedagogical purposes of aiding the reader in understanding the invention and the concepts contributed by the inventor to further the art, and are not to be construed as limitations to such specifically recited examples and conditions, nor does the organization of such examples in the specification relate to a showing of the superiority and inferiority of the invention. Although one or more embodiments of the present invention have been described in detail, it should be understood that various changes, substitutions, and alterations could be made hereto without departing from the spirit and scope of the invention. 

What is claimed is:
 1. An information processing apparatus comprising: a first communication apparatus; and a second communication apparatus configured to be connected to the first communication apparatus via a plurality of transmission paths, wherein the first communication apparatus includes: a transmitter configured to transmit, in response to designation of a transmission path targeted for diagnosis, selected amongst the transmission paths while the first communication apparatus is in a state capable of data communication with the second communication apparatus using the transmission paths, a test signal to the targeted transmission path while the state capable of data communication with the second communication apparatus is maintained by use of remaining transmission paths of the transmission paths other than the targeted transmission path, and a processor configured to perform a procedure including diagnosing presence or absence of an abnormality sign in the targeted transmission path based on a result of detecting the test signal in the targeted transmission path and outputting a diagnostic result.
 2. The information processing apparatus according to claim 1, wherein: the procedure further includes: causing, at a start of the data communication with the second communication apparatus, the transmitter to transmit the test signal to each of the transmission paths and detecting, with respect to each of the transmission paths, a first rise time of rising transitions of the test signal in a waveform, and determining, in response to the test signal transmitted to the targeted transmission path after the designation of the targeted transmission path, whether a second rise time of rising transitions of the test signal in a waveform detected in the targeted transmission path is included in a determination range determined on a basis of the first rise time detected in the targeted transmission path, and diagnosing the presence or absence of an abnormality sign in the targeted transmission path based on a result of the determining.
 3. The information processing apparatus according to claim 1, wherein: the transmitter includes: a test signal outputting unit configured to supply the test signal to a first input terminal amongst a plurality of input terminals, a data outputting unit configured to supply data to be transmitted to the second communication apparatus by distributing the data across a plurality of second input terminals, which are remaining input terminals of the input terminals other than the first input terminal and whose count is the same as a count of the transmission paths, and a switch configured to switch connection lines between the input terminals and the transmission paths, and the procedure further includes: controlling the switch to connect the second input terminals one-to-one to the transmission paths when data transmission to the second communication apparatus is performed using the transmission paths, and controlling the switch to change connection of the targeted transmission path amongst the transmission paths to the first input terminal when the data transmission to the second communication apparatus is performed using the remaining transmission paths.
 4. The information processing apparatus according to claim 3, wherein: the procedure further includes controlling the switch to change, when, amongst the transmission paths, a first transmission path having been used as a main transmission path specified in a communication protocol is designated as the targeted transmission path, connection of the first transmission path to the first input terminal and also change connection of a third input terminal amongst the second input terminals, which has been connected to the first transmission path, to a second transmission path amongst the transmission paths other than the first transmission path to thereby maintain the second transmission path in an enabled condition as the main transmission path.
 5. The information processing apparatus according to claim 1, further comprising: a diagnosis control apparatus configured to sequentially select the targeted transmission path amongst the transmission paths and present the designation of the selected targeted transmission path to the first communication apparatus.
 6. The information processing apparatus according to claim 5, wherein: when a count of the transmission paths is equal to or below a predetermined threshold in causing the diagnosis on the targeted transmission path to be performed by presenting the designation of the targeted transmission path, the diagnosis control apparatus configures a setting in the first communication apparatus to extend a timeout period for a response from the second communication apparatus to the data communication from the first communication apparatus to the second communication apparatus.
 7. The information processing apparatus according to claim 5, further comprising: a first communication apparatus group and a second communication apparatus group, each configured to include the first communication apparatus and the second communication apparatus; and a third communication apparatus configured to distribute data to be transmitted between the first communication apparatus included in the first communication apparatus group and the first communication apparatus included in the second communication apparatus group, wherein in causing the diagnosis on the targeted transmission path to be performed by presenting the designation of the targeted transmission path to the first communication apparatus included in the first communication apparatus group, the diagnosis control apparatus instructs the third communication apparatus to decrease a ratio of a data amount distributed to the first communication apparatus included in the first communication apparatus group.
 8. The information processing apparatus according to claim 5, further comprising: a plurality of communication apparatus groups each configured to include the first communication apparatus and the second communication apparatus, wherein, based on diagnosis sequence information, the diagnosis control apparatus determines which transmission path included in which communication apparatus group amongst the communication apparatus groups is to be designated as the targeted transmission path, and the diagnosis sequence information registers, when a first communication apparatus group amongst the communication apparatus groups is located on a first communication channel and each of second communication apparatus groups amongst the communication apparatus groups is located on one of a plurality of second communication channels branching off from the first communication channel and then connected to a single apparatus, combinations of transmission paths each designated as the targeted transmission path at same time based on a difference or a ratio between a count of the transmission paths included in the first communication apparatus group and a total count of the transmission paths included in each of the second communication apparatus groups, each of the combinations of transmission paths being composed of a transmission path selected from the transmission paths included in the communication apparatus groups and a transmission path selected from the transmission paths included in the individual second communication apparatus groups.
 9. The information processing apparatus according to claim 1, wherein: the first communication apparatus is connected to the second communication apparatus via an auxiliary transmission path in addition to the transmission paths, and when the targeted transmission path is designated during the data communication with the second communication apparatus using the transmission paths, the transmitter transmits the test signal to the targeted transmission path while continuing the data communication with the second communication apparatus by use of the remaining transmission paths and the auxiliary transmission path.
 10. A diagnosis control apparatus comprising: a processor configured to perform a procedure including designating, while a first communication apparatus is in a state capable of data communication with a second communication apparatus using a plurality of transmission paths, a transmission path targeted for diagnosis amongst the transmission paths to the first communication apparatus to thereby cause the first communication apparatus to perform a diagnostic operation to transmit a test signal to the targeted transmission path while continuing the state capable of data communication with the second communication apparatus by use of remaining transmission paths of the transmission paths other than the targeted transmission path; and a receiver configured to receive, from the first communication apparatus, a diagnostic result of presence or absence of an abnormality sign in the targeted transmission path, the diagnostic result being based on a result of detecting the test signal in the targeted transmission path.
 11. The diagnosis control apparatus according to claim 10, wherein: the procedure further includes configuring, when a count of the transmission paths is equal to or below a predetermined threshold in causing the diagnosis on the targeted transmission path to be performed by designating the targeted transmission path, a setting in the first communication apparatus to extend a timeout period for a response from the second communication apparatus to the data communication from the first communication apparatus to the second communication apparatus.
 12. The diagnosis control apparatus according to claim 10, wherein: when a first communication apparatus group and a second communication apparatus group are present, each of which is configured to include the first communication apparatus and the second communication apparatus, and the first communication apparatus included in the first communication apparatus group and the first communication apparatus included in the second communication apparatus group are installed in a third communication apparatus, the diagnosis control apparatus instructs, in causing the diagnosis on the targeted transmission path to be performed by designating the targeted transmission path to the first communication apparatus included in the first communication apparatus group, the third communication apparatus to decrease a data amount distributed to the first communication apparatus included in the first communication apparatus group when the third communication apparatus distributes transmission data according to a data amount distribution ratio between the first communication apparatus included in the first communication apparatus group and the first communication apparatus included in the second communication apparatus group.
 13. A communication apparatus comprising: a transmitter configured to transmit, in response to designation of a transmission path targeted for diagnosis selected amongst a plurality of transmission paths while the communication apparatus is in a state capable of data communication with a different communication apparatus using the transmission paths, a test signal to the targeted transmission path while the state capable of data communication with the different communication apparatus is maintained by use of remaining transmission paths of the transmission paths other than the targeted transmission path; and a processor configured to perform a procedure including diagnosing presence or absence of an abnormality sign in the targeted transmission path based on a result of detecting the test signal in the targeted transmission path and outputting a diagnostic result.
 14. The communication apparatus according to claim 13, wherein: the procedure further includes: causing, at a start of the data communication with the different communication apparatus, the transmitter to transmit the test signal to each of the transmission paths and detecting, with respect to each of the transmission paths, a first rise time of rising transitions of the test signal in a waveform, and determining, in response to the test signal transmitted to the targeted transmission path after the designation of the targeted transmission path, whether a second rise time of rising transitions of the test signal in a waveform detected in the targeted transmission path is included in a determination range determined on a basis of the first rise time detected in the targeted transmission path, and diagnosing the presence or absence of an abnormality sign in the targeted transmission path based on a result of the determining.
 15. The communication apparatus according to claim 13, wherein: the transmitter includes: a test signal outputting unit configured to supply the test signal to a first input terminal amongst a plurality of input terminals, a data outputting unit configured to supply data to be transmitted to the different communication apparatus by distributing the data across a plurality of second input terminals, which are remaining input terminals of the input terminals other than the first input terminal and whose count is the same as a count of the transmission paths, and a switch configured to switch connection lines between the input terminals and the transmission paths, and the procedure further includes: controlling the switch to connect the second input terminals one-to-one to the transmission paths when data transmission to the different communication apparatus is performed using the transmission paths, and controlling the switch to change connection of the targeted transmission path amongst the transmission paths to the first input terminal when the data transmission to the different communication apparatus is performed using the remaining transmission paths. 